[openstack-ansible][magnum]

Ignazio Cassano ignaziocassano at gmail.com
Thu Feb 7 09:07:33 UTC 2019


Hi Alfredo, I know some utilities are not installed on the fedora image but
on my installation it is not a problem.
As you wrote there are some issues on networking.
I've never used openstack-ansible, so I cannot help you.
I am sorry
Ignazio

Il giorno gio 7 feb 2019 alle ore 09:17 Alfredo De Luca <
alfredo.deluca at gmail.com> ha scritto:

> hi Ignazio. Unfortunately doesn't resolve either with ping or curl ....
> but what is strange also it doesn't have yum or dnf o any installer
> ....unless it use only atomic.....
>
> I think at the end it\s the issue with the network as I found out my
> all-in-one deployment doesn't have the br-ex which it supposed to be the
> external network interface.
>
> I installed OS with ansible-openstack
>
>
> Cheers
>
>
> On Wed, Feb 6, 2019 at 3:39 PM Ignazio Cassano <ignaziocassano at gmail.com>
> wrote:
>
>> Alfredo it is very strange you can ping 8.8.8.8 but you cannot resolve
>> names.  I think atomic command uses names for finishing master installation.
>> Curl is installed on master....
>>
>>
>> Il giorno Mer 6 Feb 2019 09:00 Alfredo De Luca <alfredo.deluca at gmail.com>
>> ha scritto:
>>
>>> Hi Ignazio. sorry for late reply. security group is fine. It\s not
>>> blocking the network traffic.
>>>
>>> Not sure why but, with this fedora release I can finally find atomic but
>>> there is no yum,nslookup,dig,host command..... why is so different from
>>> another version (latest) which had yum but not atomic.
>>>
>>> It's all weird
>>>
>>>
>>> Cheers
>>>
>>>
>>>
>>>
>>> On Mon, Feb 4, 2019 at 5:46 PM Ignazio Cassano <ignaziocassano at gmail.com>
>>> wrote:
>>>
>>>> Alfredo, try to check security group linked to your kubemaster.
>>>>
>>>> Il giorno Lun 4 Feb 2019 14:25 Alfredo De Luca <
>>>> alfredo.deluca at gmail.com> ha scritto:
>>>>
>>>>> Hi Ignazio. Thanks for the link...... so
>>>>>
>>>>> Now at least atomic is present on the system.
>>>>> Also I ve already had 8.8.8.8 on the system. So I can connect on the
>>>>> floating IP to the kube master....than I can ping 8.8.8.8 but for example
>>>>> doesn't resolve the names...so if I ping 8.8.8.8
>>>>> *root at my-last-wdikr74tynij-master-0 log]# ping 8.8.8.8*
>>>>> *PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.*
>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=1 ttl=118 time=12.1
>>>>> ms*
>>>>> *64 bytes from 8.8.8.8 <http://8.8.8.8>: icmp_seq=2 ttl=118 time=12.2
>>>>> ms*
>>>>>
>>>>> but if I ping google.com doesn't resolve. I can't either find on
>>>>> fedora dig or nslookup to check
>>>>> resolv.conf has
>>>>> *search openstacklocal my-last-wdikr74tynij-master-0.novalocal*
>>>>> *nameserver 8.8.8.8*
>>>>>
>>>>> It\s all so weird.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Feb 4, 2019 at 1:02 PM Ignazio Cassano <
>>>>> ignaziocassano at gmail.com> wrote:
>>>>>
>>>>>> I also suggest to change dns in your external network used by magnum.
>>>>>> Using openstack dashboard you can change it to 8.8.8.8 (If I remember
>>>>>> fine  you wrote that you can ping 8.8.8.8 from kuke baster)
>>>>>>
>>>>>> Il giorno lun 4 feb 2019 alle ore 12:39 Alfredo De Luca <
>>>>>> alfredo.deluca at gmail.com> ha scritto:
>>>>>>
>>>>>>> thanks ignazio
>>>>>>> Where can I get it from?
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Feb 4, 2019 at 11:45 AM Ignazio Cassano <
>>>>>>> ignaziocassano at gmail.com> wrote:
>>>>>>>
>>>>>>>> I used  fedora-magnum-27-4 and it works
>>>>>>>>
>>>>>>>> Il giorno lun 4 feb 2019 alle ore 09:42 Alfredo De Luca <
>>>>>>>> alfredo.deluca at gmail.com> ha scritto:
>>>>>>>>
>>>>>>>>> Hi Clemens.
>>>>>>>>> So the image I downloaded is this
>>>>>>>>> https://download.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190121.0.x86_64.qcow2
>>>>>>>>> which is the latest I think.
>>>>>>>>> But you are right...and I noticed that too.... It doesn't have
>>>>>>>>> atomic binary
>>>>>>>>> the os-release is
>>>>>>>>>
>>>>>>>>> *NAME=Fedora*
>>>>>>>>> *VERSION="29 (Cloud Edition)"*
>>>>>>>>> *ID=fedora*
>>>>>>>>> *VERSION_ID=29*
>>>>>>>>> *PLATFORM_ID="platform:f29"*
>>>>>>>>> *PRETTY_NAME="Fedora 29 (Cloud Edition)"*
>>>>>>>>> *ANSI_COLOR="0;34"*
>>>>>>>>> *CPE_NAME="cpe:/o:fedoraproject:fedora:29"*
>>>>>>>>> *HOME_URL="https://fedoraproject.org/
>>>>>>>>> <https://fedoraproject.org/>"*
>>>>>>>>> *DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/
>>>>>>>>> <https://docs.fedoraproject.org/en-US/fedora/f29/system-administrators-guide/>"*
>>>>>>>>> *SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help
>>>>>>>>> <https://fedoraproject.org/wiki/Communicating_and_getting_help>"*
>>>>>>>>> *BUG_REPORT_URL="https://bugzilla.redhat.com/
>>>>>>>>> <https://bugzilla.redhat.com/>"*
>>>>>>>>> *REDHAT_BUGZILLA_PRODUCT="Fedora"*
>>>>>>>>> *REDHAT_BUGZILLA_PRODUCT_VERSION=29*
>>>>>>>>> *REDHAT_SUPPORT_PRODUCT="Fedora"*
>>>>>>>>> *REDHAT_SUPPORT_PRODUCT_VERSION=29*
>>>>>>>>> *PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy
>>>>>>>>> <https://fedoraproject.org/wiki/Legal:PrivacyPolicy>"*
>>>>>>>>> *VARIANT="Cloud Edition"*
>>>>>>>>> *VARIANT_ID=cloud*
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> so not sure why I don't have atomic tho
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Sat, Feb 2, 2019 at 7:53 PM Clemens <
>>>>>>>>> clemens.hardewig at crandale.de> wrote:
>>>>>>>>>
>>>>>>>>>> Now to the failure of your part-013: Are you sure that you used
>>>>>>>>>> the glance image ‚fedora-atomic-latest‘ and not some other fedora image?
>>>>>>>>>> Your error message below suggests that your image does not contain ‚atomic‘
>>>>>>>>>> as part of the image …
>>>>>>>>>>
>>>>>>>>>> + _prefix=docker.io/openstackmagnum/
>>>>>>>>>> + atomic install --storage ostree --system --system-package no
>>>>>>>>>> --set REQUESTS_CA_BUNDLE=/etc/pki/tls/certs/ca-bundle.crt --name
>>>>>>>>>> heat-container-agent
>>>>>>>>>> docker.io/openstackmagnum/heat-container-agent:queens-stable
>>>>>>>>>> ./part-013: line 8: atomic: command not found
>>>>>>>>>> + systemctl start heat-container-agent
>>>>>>>>>> Failed to start heat-container-agent.service: Unit
>>>>>>>>>> heat-container-agent.service not found.
>>>>>>>>>>
>>>>>>>>>> Am 02.02.2019 um 17:36 schrieb Alfredo De Luca <
>>>>>>>>>> alfredo.deluca at gmail.com>:
>>>>>>>>>>
>>>>>>>>>> Failed to start heat-container-agent.service: Unit
>>>>>>>>>> heat-container-agent.service not found.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> *Alfredo*
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> *Alfredo*
>>>>>>>
>>>>>>>
>>>>>
>>>>> --
>>>>> *Alfredo*
>>>>>
>>>>>
>>>
>>> --
>>> *Alfredo*
>>>
>>>
>
> --
> *Alfredo*
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20190207/2d907316/attachment.html>


More information about the openstack-discuss mailing list