text:
Can't render Buefy components when customizing Buefy with constructors

Overview of the problem
Buefy version: 0.6.3
Vuejs version: 2.5.13
OS/Browser: Google Chrome
Description
Buefy components fail to load when I attempt to customise Buefy with the constructors instead of using the default values. If it matters, I set this up to work standalone without importing via node or webpack. The components also load without errors if I use Vue.use(Buefy.default);
Steps to reproduce

Import the necessary css and js
Define the constructors like mentioned in https://buefy.github.io/#/documentation/constructor-options instead of using Vue.use(Buefy.default);
Insert a Buefy component to your HTML and mount a vue instance to the html

Expected behavior
Buefy component should appear as expected.
Actual behavior
Browser throws error on the Buefy element

@ruust Are using npm or CDN ?

@jtommy CDN. Updated my issue description!

Could you provide us your code? Without constructor options is it works?

@jtommy Refer to https://jsfiddle.net/am0n1hsj/. Comment out the Constructors and using Vue.use(Buefy.default); line would result in the datepicker appearing.

@ruust When you use CDN, you have to use Buefy.default with or without constructor options.

authors: jtommy ruust


text:
Send user data on successful login - BE

The server should send the user data in the response for successful login

The back-end need not send the user data on login. The front-end will request it later when other pages are loaded.
Closing this issue.

source: gharchive/issue

repo: raghavan-renganathan/undefined

license: mit

license_type: permissive

license_source: bigquery


text:
Use SHA256 for hashlocks

because it's used more commonly.

The change is straightforward.

source: gharchive/pull-request

repo: raiden-network/raiden-contracts

license: MIT

license_source: github-api


text:
Preserve eq_any with empty collection behavior.

Preserve and ensure the behavior does not change in Future 5-0-stable branch for eq_any with an empty collection as input.  This has already changed in the 6-0-stable (breaking change).  See issue #368

r? @sgrif

Just to be clear I'm not asking for the current 6-0-stable to be changed.  I only would like to add this test to protect existing behavior in 5-0-stable.

:+1:

authors: danielpclark rafaelfranca rajcybage

repo: rails/arel


text:
Yesterday I could run my application, but today I can't run my application anymore because 'Framework opencv_dart not found'.

Launching lib/main.dart on iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: ----
Running Xcode build...
Xcode build done.                                           33.6s
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Framework 'opencv_dart' not found
Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)
Error launching application on iPhone.

provide the following information please:

have you tried to clean and rerun?
which version?
have you run setup?
the output of setup.

This error show when i try to run app
For the flutter pub get i have no issue

Yes ,i do.
Flutter version
Flutter (Channel stable, 3.19.2, on macOS 14.4 23E214 darwin-arm64, locale en-ID)
Xcode version
Xcode 15.1.
Yes ,i do.
Output of setup
Launching lib/main.dart on iPhone in debug mode...
Automatically signing iOS for device deployment using specified development team in Xcode project: ----
Running Xcode build...
Xcode build done. 33.6s
Failed to build iOS app
Could not build the precompiled application for the device.
Error (Xcode): Framework 'opencv_dart' not found

Error (Xcode): Linker command failed with exit code 1 (use -v to see invocation)
Error launching application on iPhone.

Which version of opencv_dart?

3,4. Setup means dart run opencv_dart:setup

ohhh i see,i skip this part thanks.

authors: IzraelAA rainyl


text:
🛑 RiotSkin4CN-Download is down

In caf4af2, RiotSkin4CN-Download (https://s-cd-4307-general.oss.dogecdn.com/riotskin4cn/live.json) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RiotSkin4CN-Download is back up in b229495.


text:
wrong block explorer link on homepage

On clicking Block explorer Icon on home page, it's redirecting to wrong link
e.g.  https://basescan.org/address/undefined

In latest main branch, this icon is not displayed on Home page

repo: rairprotocol/rair-official-library


text:
export isLoop and none for easier changes to combineReducers

based on https://github.com/raisemarketplace/redux-loop/pull/53 but also exports none, which is needed by combineReducers.optimizeBatch

none is already exported as part of Effects

True fact.

@emmby thanks for your contribution anyway!

authors: bdwain emmby lukewestby

repo: raisemarketplace/redux-loop


text:
🛑 Hacker News is down

In 2ce1597, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 312 ms

Resolved: Hacker News is back up in c479f54 after 1,108 days, 12 hours, 29 minutes.

repo: rajcharin/upptime


text:
fix(core): removed exclusive textview

removed exclusive use of 'TextView'

LTGM.

authors: ashton-szabo gauravakumar

repo: rakutentech/ui-automation-tools-mbt


text:
check for outdated bee version

and highlight outdated version if new bee is available

fixed in https://github.com/rampall/doctor-bee/commit/6264018fa602d3e90caaa0fba4ad793c87d91dac

repo: rampall/doctor-bee


text:
Behaviour of yf download when certain symbols fail to download (no error bug!)

If yf download fails to download certain symbols, it should continue and go to the next symbol without generating a bug.
The pre-release version yfinance-0.2.19b3 generates a bug when there is a symbol that could not be downloaded:
https://github.com/ranaroussi/yfinance/issues/1526#issuecomment-1559588523
However, the release-version 0.2.18 simply says that the download failed but continues to download the next symbols WITHOUT generating an error bug:
https://github.com/ranaroussi/yfinance/issues/1526#issuecomment-1559707072
Describe the solution
When the user gives a long list of tickers to yf.download, chances are that some tickers can not be downloaded. If this is the case, yf-download should simply continue with the next symbol without generating a bug. It should simply continue to behave like up to version 0.2.18.
Additional context

generates a bug

Then please use the 'Bug report' template not 'Feature request'

repo: ranaroussi/yfinance


text:
get_news() returns news not related to the given ticker

Describe bug
I used yfinance to get news from different companies listed on various stock exchanges using method news (.get_news()) and it worked very well.
However, starting from March 2024 the get_news() method returns news not related to given ticker. I believe it now returns news from the main page of Yahoo Finance (see Bad data proof. For example, I asked about "1A9.F" ticker and it returned 'relatedTickers': ['CMOPF'] news)
Simple code that reproduces your problem
import yfinance as yf
msft = yf.Ticker("1A9.F")
msft.news

Debug log
DEBUG    Entering get()
DEBUG     url=https://query2.finance.yahoo.com/v1/finance/search?q=1A9.F
DEBUG     params=None
DEBUG     Entering _get_cookie_and_crumb()
DEBUG      cookie_mode = 'basic'
DEBUG      Entering _get_cookie_and_crumb_basic()
DEBUG       loaded persistent cookie
DEBUG       reusing cookie
DEBUG       crumb = 'f/nSB8VksED'
DEBUG      Exiting _get_cookie_and_crumb_basic()
DEBUG     Exiting _get_cookie_and_crumb()
DEBUG     response code=200
DEBUG    Exiting get()

Bad data proof
{'count': 13,
 'explains': [],
 'lists': [{'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 0.8398355065208919,
            'followerCount': 61456,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/110f1012357c7b3e87d14912e7023f819b61278e7f0e90a3825821d2ef3c427c/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/most-bought-activist.png',
            'index': 'most-bought-by-activist-hedge-funds',
            'name': 'Most Bought By Activist Hedge Funds',
            'pfId': 'most_bought_by_activist_hedge_funds',
            'score': 15.645953,
            'slug': 'most-bought-by-activist-hedge-funds',
            'symbolCount': 18,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 0.5050837217231051,
            'followerCount': 41686,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/f1b1a50dcfdddcf42a67d2da1bb1c341e6f65992b3d89154b9020ae8a9ffa004/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/mostboughtHedgeFunds.png',
            'index': 'most-bought-by-hedge-funds',
            'name': 'Most Bought By Hedge Funds',
            'pfId': 'most_bought_by_hedge_funds',
            'score': 10.904234,
            'slug': 'most-bought-by-hedge-funds',
            'symbolCount': 30,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 1.119014997698063,
            'followerCount': 29897,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/9f2d41c327a5d20c8062b14f526038441141d5644b2b3a0efee2e12d9be1efe0/finance/resizefill_w96_h96/https://s.yimg.com/uc/finance/social/portfolio/most-watched.png',
            'index': 'most-watched',
            'name': 'Most Watched by Yahoo Finance Users',
            'pfId': 'most_watched',
            'score': 7.611414,
            'slug': 'most-watched',
            'symbolCount': 30,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'trea',
            'dailyPercentGain': -0.2682118695951419,
            'followerCount': 23819,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/3c7c7b592c7aba2beee72abb1e520b85d6241aee639ea2e8033b96962ad2e126/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/iStock-476433472.png',
            'index': 'the-fight-against-covid19',
            'name': 'The Fight Against COVID19',
            'pfId': 'the_fight_against_covid19',
            'score': 6.4065385,
            'slug': 'the-fight-against-covid19',
            'symbolCount': 13,
            'type': 'ALGO_WATCHLIST',
            'userId': 'X3NJ2A7VDSABUI4URBWME2PZNM'}],
 'nav': [],
 'news': [{'link': 'https://finance.yahoo.com/m/41621b45-a35e-3ee7-9bfc-83208f5ef88b/warren-buffett-vs.-carl.html',
           'providerPublishTime': 1717391040,
           'publisher': 'Motley Fool',
           'relatedTickers': ['IEP'],
           'thumbnail': {'resolutions': [{'height': 933,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/7BnUe4BeZ..bO6lLQiG3bg--~B/aD05MzM7dz0xNDAwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/motleyfool.com/9b1a29f472887a127d65d8a72b330520',
                                          'width': 1400},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/qV4yrQGnvrOhp7Fa395lrw--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/motleyfool.com/9b1a29f472887a127d65d8a72b330520',
                                          'width': 140}]},
           'title': 'Warren Buffett vs. Carl Icahn: Is Berkshire Hathaway or '
                    'Icahn Enterprises a Better Stock for You?',
           'type': 'STORY',
           'uuid': '41621b45-a35e-3ee7-9bfc-83208f5ef88b'},
          {'link': 'https://finance.yahoo.com/news/analysis-trial-investors-weigh-trump-050333950.html',
           'providerPublishTime': 1717391013,
           'publisher': 'Reuters',
           'thumbnail': {'resolutions': [{'height': 533,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/fxWMIZxYI0EUrxpXdLnJXw--~B/aD01MzM7dz04MDA7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/reuters-finance.com/9c25d93290d6c1bce07a03726d8cfebf',
                                          'width': 800},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/TKLIoWj6NLK673W.kZxJzQ--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/reuters-finance.com/9c25d93290d6c1bce07a03726d8cfebf',
                                          'width': 140}]},
           'title': 'Analysis-After trial, investors weigh Trump 2.0 factor as '
                    'election looms',
           'type': 'STORY',
           'uuid': 'acf48aba-d381-3c12-95c6-4fbc0c335aa3'},
          {'link': 'https://finance.yahoo.com/m/87a0f0e5-7ebd-390d-a58d-2e22605357cc/dow-jones-futures-rise%3B.html',
           'providerPublishTime': 1717390973,
           'publisher': "Investor's Business Daily",
           'relatedTickers': ['NVDA', '^GSPC', '^DJI', 'COMP', 'QCOM'],
           'thumbnail': {'resolutions': [{'height': 563,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/vN4.NUyvgiN_4UzIAKqlBQ--~B/aD01NjM7dz0xMDAwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/ibd.com/a0e93b56357fe572742d0fcf66117149',
                                          'width': 1000},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/5zGENOL9gogmWSQfoXJyZg--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/ibd.com/a0e93b56357fe572742d0fcf66117149',
                                          'width': 140}]},
           'title': 'Dow Jones Futures Rise; Nvidia CEO Touts Next AI Chips, '
                    'And So Does AMD',
           'type': 'STORY',
           'uuid': '87a0f0e5-7ebd-390d-a58d-2e22605357cc'},
          {'link': 'https://finance.yahoo.com/news/cosmo-bring-real-time-ai-050200583.html',
           'providerPublishTime': 1717390920,
           'publisher': 'Newsfile',
           'relatedTickers': ['CMOPF'],
           'title': 'Cosmo to Bring Real-Time AI into Intelligent Medical '
                    'Devices with NVIDIA IGX',
           'type': 'STORY',
           'uuid': '0ccd689d-f2c2-3863-bc7e-9f7e149e5209'},
          {'link': 'https://finance.yahoo.com/news/formosa-laboratories-completes-acquisition-synchem-050100973.html',
           'providerPublishTime': 1717390860,
           'publisher': 'PR Newswire',
           'thumbnail': {'resolutions': [{'height': 16,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/C5YjYIGSs0oai2fzZGJL5w--~B/aD0xNjt3PTE2O2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/f2c7aa95a346d7cd28e0120b7e61e4c6',
                                          'width': 16},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/dy5WZBH1sCwBZhngOOveZw--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/f2c7aa95a346d7cd28e0120b7e61e4c6',
                                          'width': 140}]},
           'title': 'Formosa Laboratories Completes the Acquisition of Synchem '
                    'to Expand North American CDMO Footprint',
           'type': 'STORY',
           'uuid': '2469b825-9891-3edd-9117-bd53abbc27b4'},
          {'link': 'https://finance.yahoo.com/news/alk-presents-positive-phase-3-050000824.html',
           'providerPublishTime': 1717390800,
           'publisher': 'GlobeNewswire',
           'relatedTickers': ['AKBLF'],
           'thumbnail': {'resolutions': [{'height': 39,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/TFRWuPjwySPHeuzcZu7baA--~B/aD0zOTt3PTE0MjthcHBpZD15dGFjaHlvbg--/https://media.zenfs.com/en/globenewswire.com/848fac2aa05860966f3ec6e476ae2174',
                                          'width': 142},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/ThuNbcPP_Feh2fkyTF1kLA--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/globenewswire.com/848fac2aa05860966f3ec6e476ae2174',
                                          'width': 140}]},
           'title': 'ALK presents positive phase 3 paediatric trial data '
                    'offering new hope for children with respiratory allergies',
           'type': 'STORY',
           'uuid': '03b1801d-740e-3e3c-8e32-35ae99f88f74'},
          {'link': 'https://finance.yahoo.com/news/uae-host-games-future-2025-050000491.html',
           'providerPublishTime': 1717390800,
           'publisher': 'PR Newswire',
           'thumbnail': {'resolutions': [{'height': 267,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/OSxSsuhRfOm.xhRvI8EnDA--~B/aD0yNjc7dz00MDA7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/prnewswire.com/787202b2246b38029f0bbe86ecc77e2e',
                                          'width': 400},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/JPxiXY91JZUYybL6Xz9.8A--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/787202b2246b38029f0bbe86ecc77e2e',
                                          'width': 140}]},
           'title': 'UAE TO HOST GAMES OF THE FUTURE 2025',
           'type': 'STORY',
           'uuid': '160df24c-fc26-34ce-9879-09c29aa5bc1c'},
          {'link': 'https://finance.yahoo.com/news/start-day-message-050000714.html',
           'providerPublishTime': 1717390800,
           'publisher': 'GlobeNewswire',
           'title': 'Start of Day Message',
           'type': 'STORY',
           'uuid': '218e0d81-069c-3803-b0db-d14c1cffe14d'}],
 'quotes': [{'exchDisp': 'Frankfurt',
             'exchange': 'FRA',
             'index': 'quotes',
             'industry': 'Gold',
             'industryDisp': 'Gold',
             'isYahooFinance': True,
             'longname': 'Asante Gold Corporation',
             'quoteType': 'EQUITY',
             'score': 2000100.0,
             'sector': 'Basic Materials',
             'sectorDisp': 'Basic Materials',
             'shortname': 'ASANTE GOLD CORP.',
             'symbol': '1A9.F',
             'typeDisp': 'Equity'}],
 'researchReports': [],
 'screenerFieldResults': [],
 'timeTakenForAlgowatchlist': 400,
 'timeTakenForCrunchbase': 0,
 'timeTakenForCulturalAssets': 0,
 'timeTakenForNav': 400,
 'timeTakenForNews': 700,
 'timeTakenForPredefinedScreener': 400,
 'timeTakenForQuotes': 428,
 'timeTakenForResearchReports': 0,
 'timeTakenForScreenerField': 0,
 'totalTime': 37}

yfinance version
0.2.40
Python version
3.10
Operating system
Windows

I see this issue as well.
import yfinance as yf

stock = yf.Ticker("TVSMOTOR.NS")
news = stock.news

print(news)

Returns "random" news or news from the main page.

Same issue, hopefully they will fix the endpoint soon

straight up doesnt work now?
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

straight up doesnt work now? raise RequestsJSONDecodeError(e.msg, e.doc, e.pos) requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Yes, had that yesterday. Today it worked for a while and now it is giving this error again.

straight up doesnt work now? raise RequestsJSONDecodeError(e.msg, e.doc, e.pos) requests.exceptions.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

I believe this issue arose from yfinance/data.py in YfData.get(...) line 378, in particular when the first round of cookie strategy fails (perhaps due to rate limit or typo or some other reasons), it goes into a second cookie strategy, but the response is returned regardless of status code for the second round, so if the second request also returned 4xx status code and response.json() is called it'll raise a JSON decode error.
    @utils.log_indent_decorator
    def get(self, url, user_agent_headers=None, params=None, proxy=None, timeout=30):
        # Important: treat input arguments as immutable.

        if len(url) > 200:
            utils.get_yf_logger().debug(f'url={url[:200]}...')
        else:
            utils.get_yf_logger().debug(f'url={url}')
        utils.get_yf_logger().debug(f'params={params}')
        proxy = self._get_proxy(proxy)

        if params is None:
            params = {}
        if 'crumb' in params:
            raise Exception("Don't manually add 'crumb' to params dict, let data.py handle it")

        cookie, crumb, strategy = self._get_cookie_and_crumb()
        if crumb is not None:
            crumbs = {'crumb': crumb}
        else:
            crumbs = {}
        if strategy == 'basic' and cookie is not None:
            # Basic cookie strategy adds cookie to GET parameters
            cookies = {cookie.name: cookie.value}
        else:
            cookies = None

        request_args = {
            'url': url,
            'params': {**params, **crumbs},
            'cookies': cookies,
            'proxies': proxy,
            'timeout': timeout,
            'headers': user_agent_headers or self.user_agent_headers
        }
        response = self._session.get(**request_args)
        utils.get_yf_logger().debug(f'response code={response.status_code}')
        if response.status_code >= 400:
            # Retry with other cookie strategy
            if strategy == 'basic':
                self._set_cookie_strategy('csrf')
            else:
                self._set_cookie_strategy('basic')
            cookie, crumb, strategy = self._get_cookie_and_crumb(proxy, timeout)
            request_args['params']['crumb'] = crumb
            if strategy == 'basic':
                request_args['cookies'] = {cookie.name: cookie.value}
            response = self._session.get(**request_args)
            utils.get_yf_logger().debug(f'response code={response.status_code}')

        return response

Adding a second status code check would prevent the error from being raised, and perhaps a wait period or backoff loop before going into the second strategy.

Describe bug
I used yfinance to get news from different companies listed on various stock exchanges using method news (.get_news()) and it worked very well.
However, starting from March 2024 the get_news() method returns news not related to given ticker. I believe it now returns news from the main page of Yahoo Finance (see Bad data proof. For example, I asked about "1A9.F" ticker and it returned 'relatedTickers': ['CMOPF'] news)
Simple code that reproduces your problem
import yfinance as yf
msft = yf.Ticker("1A9.F")
msft.news

Debug log
DEBUG    Entering get()
DEBUG     url=https://query2.finance.yahoo.com/v1/finance/search?q=1A9.F
DEBUG     params=None
DEBUG     Entering _get_cookie_and_crumb()
DEBUG      cookie_mode = 'basic'
DEBUG      Entering _get_cookie_and_crumb_basic()
DEBUG       loaded persistent cookie
DEBUG       reusing cookie
DEBUG       crumb = 'f/nSB8VksED'
DEBUG      Exiting _get_cookie_and_crumb_basic()
DEBUG     Exiting _get_cookie_and_crumb()
DEBUG     response code=200
DEBUG    Exiting get()

Bad data proof
{'count': 13,
 'explains': [],
 'lists': [{'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 0.8398355065208919,
            'followerCount': 61456,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/110f1012357c7b3e87d14912e7023f819b61278e7f0e90a3825821d2ef3c427c/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/most-bought-activist.png',
            'index': 'most-bought-by-activist-hedge-funds',
            'name': 'Most Bought By Activist Hedge Funds',
            'pfId': 'most_bought_by_activist_hedge_funds',
            'score': 15.645953,
            'slug': 'most-bought-by-activist-hedge-funds',
            'symbolCount': 18,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 0.5050837217231051,
            'followerCount': 41686,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/f1b1a50dcfdddcf42a67d2da1bb1c341e6f65992b3d89154b9020ae8a9ffa004/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/mostboughtHedgeFunds.png',
            'index': 'most-bought-by-hedge-funds',
            'name': 'Most Bought By Hedge Funds',
            'pfId': 'most_bought_by_hedge_funds',
            'score': 10.904234,
            'slug': 'most-bought-by-hedge-funds',
            'symbolCount': 30,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'yahoo-finance',
            'dailyPercentGain': 1.119014997698063,
            'followerCount': 29897,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/9f2d41c327a5d20c8062b14f526038441141d5644b2b3a0efee2e12d9be1efe0/finance/resizefill_w96_h96/https://s.yimg.com/uc/finance/social/portfolio/most-watched.png',
            'index': 'most-watched',
            'name': 'Most Watched by Yahoo Finance Users',
            'pfId': 'most_watched',
            'score': 7.611414,
            'slug': 'most-watched',
            'symbolCount': 30,
            'type': 'ALGO_WATCHLIST',
            'userId': '5SSSFLJVWAMDKUGZM5HLSSBNAY'},
           {'brandSlug': 'trea',
            'dailyPercentGain': -0.2682118695951419,
            'followerCount': 23819,
            'iconUrl': 'https://edgecast-img.yahoo.net/mysterio/api/3c7c7b592c7aba2beee72abb1e520b85d6241aee639ea2e8033b96962ad2e126/finance/resizefill_w96_h96/https://s.yimg.com/uc/fin/img/iStock-476433472.png',
            'index': 'the-fight-against-covid19',
            'name': 'The Fight Against COVID19',
            'pfId': 'the_fight_against_covid19',
            'score': 6.4065385,
            'slug': 'the-fight-against-covid19',
            'symbolCount': 13,
            'type': 'ALGO_WATCHLIST',
            'userId': 'X3NJ2A7VDSABUI4URBWME2PZNM'}],
 'nav': [],
 'news': [{'link': 'https://finance.yahoo.com/m/41621b45-a35e-3ee7-9bfc-83208f5ef88b/warren-buffett-vs.-carl.html',
           'providerPublishTime': 1717391040,
           'publisher': 'Motley Fool',
           'relatedTickers': ['IEP'],
           'thumbnail': {'resolutions': [{'height': 933,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/7BnUe4BeZ..bO6lLQiG3bg--~B/aD05MzM7dz0xNDAwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/motleyfool.com/9b1a29f472887a127d65d8a72b330520',
                                          'width': 1400},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/qV4yrQGnvrOhp7Fa395lrw--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/motleyfool.com/9b1a29f472887a127d65d8a72b330520',
                                          'width': 140}]},
           'title': 'Warren Buffett vs. Carl Icahn: Is Berkshire Hathaway or '
                    'Icahn Enterprises a Better Stock for You?',
           'type': 'STORY',
           'uuid': '41621b45-a35e-3ee7-9bfc-83208f5ef88b'},
          {'link': 'https://finance.yahoo.com/news/analysis-trial-investors-weigh-trump-050333950.html',
           'providerPublishTime': 1717391013,
           'publisher': 'Reuters',
           'thumbnail': {'resolutions': [{'height': 533,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/fxWMIZxYI0EUrxpXdLnJXw--~B/aD01MzM7dz04MDA7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/reuters-finance.com/9c25d93290d6c1bce07a03726d8cfebf',
                                          'width': 800},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/TKLIoWj6NLK673W.kZxJzQ--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/reuters-finance.com/9c25d93290d6c1bce07a03726d8cfebf',
                                          'width': 140}]},
           'title': 'Analysis-After trial, investors weigh Trump 2.0 factor as '
                    'election looms',
           'type': 'STORY',
           'uuid': 'acf48aba-d381-3c12-95c6-4fbc0c335aa3'},
          {'link': 'https://finance.yahoo.com/m/87a0f0e5-7ebd-390d-a58d-2e22605357cc/dow-jones-futures-rise%3B.html',
           'providerPublishTime': 1717390973,
           'publisher': "Investor's Business Daily",
           'relatedTickers': ['NVDA', '^GSPC', '^DJI', 'COMP', 'QCOM'],
           'thumbnail': {'resolutions': [{'height': 563,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/vN4.NUyvgiN_4UzIAKqlBQ--~B/aD01NjM7dz0xMDAwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/ibd.com/a0e93b56357fe572742d0fcf66117149',
                                          'width': 1000},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/5zGENOL9gogmWSQfoXJyZg--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/ibd.com/a0e93b56357fe572742d0fcf66117149',
                                          'width': 140}]},
           'title': 'Dow Jones Futures Rise; Nvidia CEO Touts Next AI Chips, '
                    'And So Does AMD',
           'type': 'STORY',
           'uuid': '87a0f0e5-7ebd-390d-a58d-2e22605357cc'},
          {'link': 'https://finance.yahoo.com/news/cosmo-bring-real-time-ai-050200583.html',
           'providerPublishTime': 1717390920,
           'publisher': 'Newsfile',
           'relatedTickers': ['CMOPF'],
           'title': 'Cosmo to Bring Real-Time AI into Intelligent Medical '
                    'Devices with NVIDIA IGX',
           'type': 'STORY',
           'uuid': '0ccd689d-f2c2-3863-bc7e-9f7e149e5209'},
          {'link': 'https://finance.yahoo.com/news/formosa-laboratories-completes-acquisition-synchem-050100973.html',
           'providerPublishTime': 1717390860,
           'publisher': 'PR Newswire',
           'thumbnail': {'resolutions': [{'height': 16,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/C5YjYIGSs0oai2fzZGJL5w--~B/aD0xNjt3PTE2O2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/f2c7aa95a346d7cd28e0120b7e61e4c6',
                                          'width': 16},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/dy5WZBH1sCwBZhngOOveZw--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/f2c7aa95a346d7cd28e0120b7e61e4c6',
                                          'width': 140}]},
           'title': 'Formosa Laboratories Completes the Acquisition of Synchem '
                    'to Expand North American CDMO Footprint',
           'type': 'STORY',
           'uuid': '2469b825-9891-3edd-9117-bd53abbc27b4'},
          {'link': 'https://finance.yahoo.com/news/alk-presents-positive-phase-3-050000824.html',
           'providerPublishTime': 1717390800,
           'publisher': 'GlobeNewswire',
           'relatedTickers': ['AKBLF'],
           'thumbnail': {'resolutions': [{'height': 39,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/TFRWuPjwySPHeuzcZu7baA--~B/aD0zOTt3PTE0MjthcHBpZD15dGFjaHlvbg--/https://media.zenfs.com/en/globenewswire.com/848fac2aa05860966f3ec6e476ae2174',
                                          'width': 142},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/ThuNbcPP_Feh2fkyTF1kLA--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/globenewswire.com/848fac2aa05860966f3ec6e476ae2174',
                                          'width': 140}]},
           'title': 'ALK presents positive phase 3 paediatric trial data '
                    'offering new hope for children with respiratory allergies',
           'type': 'STORY',
           'uuid': '03b1801d-740e-3e3c-8e32-35ae99f88f74'},
          {'link': 'https://finance.yahoo.com/news/uae-host-games-future-2025-050000491.html',
           'providerPublishTime': 1717390800,
           'publisher': 'PR Newswire',
           'thumbnail': {'resolutions': [{'height': 267,
                                          'tag': 'original',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/OSxSsuhRfOm.xhRvI8EnDA--~B/aD0yNjc7dz00MDA7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/prnewswire.com/787202b2246b38029f0bbe86ecc77e2e',
                                          'width': 400},
                                         {'height': 140,
                                          'tag': '140x140',
                                          'url': 'https://s.yimg.com/uu/api/res/1.2/JPxiXY91JZUYybL6Xz9.8A--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/prnewswire.com/787202b2246b38029f0bbe86ecc77e2e',
                                          'width': 140}]},
           'title': 'UAE TO HOST GAMES OF THE FUTURE 2025',
           'type': 'STORY',
           'uuid': '160df24c-fc26-34ce-9879-09c29aa5bc1c'},
          {'link': 'https://finance.yahoo.com/news/start-day-message-050000714.html',
           'providerPublishTime': 1717390800,
           'publisher': 'GlobeNewswire',
           'title': 'Start of Day Message',
           'type': 'STORY',
           'uuid': '218e0d81-069c-3803-b0db-d14c1cffe14d'}],
 'quotes': [{'exchDisp': 'Frankfurt',
             'exchange': 'FRA',
             'index': 'quotes',
             'industry': 'Gold',
             'industryDisp': 'Gold',
             'isYahooFinance': True,
             'longname': 'Asante Gold Corporation',
             'quoteType': 'EQUITY',
             'score': 2000100.0,
             'sector': 'Basic Materials',
             'sectorDisp': 'Basic Materials',
             'shortname': 'ASANTE GOLD CORP.',
             'symbol': '1A9.F',
             'typeDisp': 'Equity'}],
 'researchReports': [],
 'screenerFieldResults': [],
 'timeTakenForAlgowatchlist': 400,
 'timeTakenForCrunchbase': 0,
 'timeTakenForCulturalAssets': 0,
 'timeTakenForNav': 400,
 'timeTakenForNews': 700,
 'timeTakenForPredefinedScreener': 400,
 'timeTakenForQuotes': 428,
 'timeTakenForResearchReports': 0,
 'timeTakenForScreenerField': 0,
 'totalTime': 37}

yfinance version
0.2.40
Python version
3.10
Operating system
Windows

I noticed that for this particular ticker 1A9.F, when you use the full name of the company Asante Gold Corporation it seems to returns properly relevance news.
t = "1A9.F" # Using the original ticker for the first try, which gives front-page news
r = requests.get(
    url = f"https://query2.finance.yahoo.com/v1/finance/search?q={t}",
    headers = {
        'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36'
    }
)

data = r.json()
print(data)

>>> ... 'news': [{'uuid': '03ab3a06-2fca-3f0b-a94e-7728b5db1ea0',
   'title': "Parks Canada and partners take first step toward creating a national urban park in St. John's",
   'publisher': 'CNW Group',
   'link': 'https://finance.yahoo.com/news/parks-canada-partners-first-step-204500140.html',
   'providerPublishTime': 1720471500,
   'type': 'STORY',
   'thumbnail': {'resolutions': [{'url': 'https://s.yimg.com/uu/api/res/1.2/zXZUNStn6b5.lW8TIWS5MA--~B/aD0zMDA7dz00MDA7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/cnwgroup.com/bad4812fef6c57928122ed62b23bf521',
      'width': 400,
      'height': 300,
      'tag': 'original'},
     {'url': 'https://s.yimg.com/uu/api/res/1.2/3wPCwm4YhXri9JmUAow1Rg--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/cnwgroup.com/bad4812fef6c57928122ed62b23bf521',
      'width': 140,
      'height': 140,
      'tag': '140x140'}]}},
  {'uuid': 'd791484e-8417-3aae-97fc-273446fc2995',
   'title': 'Tesla Stock’s Win Streak Hits 9 Days. It Almost Didn’t Happen.',
   'publisher': 'Barrons.com',
   'link': 'https://finance.yahoo.com/m/d791484e-8417-3aae-97fc-273446fc2995/tesla-stock%E2%80%99s-win-streak-hits.html',
   'providerPublishTime': 1720471380,
   'type': 'STORY',
   'thumbnail': {'resolutions': [{'url': 'https://s.yimg.com/uu/api/res/1.2/rHL2F56x3R2OPgKJZ_LqSQ--~B/aD02NDA7dz0xMjgwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/Barrons.com/e4a0d77b5267671e4800b437969ca49d',
      'width': 1280,
      'height': 640,
      'tag': 'original'} ...

t2 = data['quotes'][0]['longname']  # If use the longname from the previous quote instead, it works

r2 = requests.get(
    url = f"https://query2.finance.yahoo.com/v1/finance/search?q={t2}",
    headers = {
        'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36'
    }
)

data2 = r2.json()

print(data2)

>>> ... {'uuid': 'bae62caa-2116-3725-8a35-7e5c5ffc0487',
  'title': 'Asante Files Financial and Operating Results for the Quarter Ended April 30, 2024',
  'publisher': 'GlobeNewswire',
  'link': 'https://finance.yahoo.com/news/asante-files-financial-operating-results-110000900.html',
  'providerPublishTime': 1718622000,
  'type': 'STORY',
  'thumbnail': {'resolutions': [{'url': 'https://s.yimg.com/uu/api/res/1.2/IoEIOReUphFfMjBXXQ2w.g--~B/aD00Mzg7dz05Njg7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 968,
     'height': 438,
     'tag': 'original'},
    {'url': 'https://s.yimg.com/uu/api/res/1.2/FAPh5S6ry5TgLH1N90GGkA--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 140,
     'height': 140,
     'tag': '140x140'}]},
  'relatedTickers': ['ASGOF']},
 {'uuid': '405254d2-bde0-3fd9-9f69-8d00a37067bf',
  'title': 'Asante Announces Project Update for the Sulphide Recovery Plant at the Bibiani Gold Mine',
  'publisher': 'GlobeNewswire',
  'link': 'https://finance.yahoo.com/news/asante-announces-project-sulphide-recovery-111500095.html',
  'providerPublishTime': 1718277300,
  'type': 'STORY',
  'thumbnail': {'resolutions': [{'url': 'https://s.yimg.com/uu/api/res/1.2/IoEIOReUphFfMjBXXQ2w.g--~B/aD00Mzg7dz05Njg7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 968,
     'height': 438,
     'tag': 'original'},
    {'url': 'https://s.yimg.com/uu/api/res/1.2/FAPh5S6ry5TgLH1N90GGkA--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 140,
     'height': 140,
     'tag': '140x140'}]},
  'relatedTickers': ['ASGOF']},
 {'uuid': '347918dd-bc9b-3853-9de1-6d2afb247150',
  'title': 'Asante Announces Rerouting of Bibiani-Goaso Highway, Paving the Way to Grow Gold Production at the Bibiani Gold Mine',
  'publisher': 'GlobeNewswire',
  'link': 'https://finance.yahoo.com/news/asante-announces-rerouting-bibiani-goaso-110000022.html',
  'providerPublishTime': 1718276400,
  'type': 'STORY',
  'thumbnail': {'resolutions': [{'url': 'https://s.yimg.com/uu/api/res/1.2/IoEIOReUphFfMjBXXQ2w.g--~B/aD00Mzg7dz05Njg7YXBwaWQ9eXRhY2h5b24-/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 968,
     'height': 438,
     'tag': 'original'},
    {'url': 'https://s.yimg.com/uu/api/res/1.2/FAPh5S6ry5TgLH1N90GGkA--~B/Zmk9ZmlsbDtoPTE0MDtweW9mZj0wO3c9MTQwO2FwcGlkPXl0YWNoeW9u/https://media.zenfs.com/en/globenewswire.com/ad2b25f2467b60b1f2b65ac649423e4a',
     'width': 140,
     'height': 140,
     'tag': '140x140'}]},
  'relatedTickers': ['ASGOF']} ...

I think it might be worth looking into adding a recursive search method, but it doesn't work every time. For instance, the same strategy fails when used with TVSMOTOR.NS. It does seem like it's more common with non-US securities tho.

After additional research, I've noticed that the function doesn't work only with tickers that have dots in their names (1A9.F, ZOMATO.NS, TVSMOTOR.NS). In other cases, everything works as intended

I think it might be worth looking into adding a recursive search method, but it doesn't work every time. For instance, the same strategy fails when used with TVSMOTOR.NS. It does seem like it's more common with non-US securities tho.

As I understand full name works only if company have ticker option without dot in name e.g. Asante Gold Corporation have several tickers (1A9.F, 1A9.DU, 1A9.BE, ASE.CN, ASGOF) and full name request works and TVS Motor Company Limited have two tickers (TVSMOTOR.BO, TVSMOTOR.NS), both with dots in name.
Also, if I use ticker without dot in original code for Asante, code returns correct news
import yfinance as yf
msft = yf.Ticker("ASGOF")
msft.news

authors: AlexPlatin SnowCheetos abrohit jamesdidit72 lkaino


text:
Trying to access Ticker objects for multiple tickers results in AttributeError

According to the documentation we can initialize multiple Ticker objects like this

import yfinance as yf
tickers = yf.Tickers('msft aapl goog')
tickers.tickers.MSFT.info
tickers.tickers.AAPL.history(period="1mo")
tickers.tickers.GOOG.actions

However, I get the following error:
print(tickers.tickers.MSFT.info)
AttributeError: 'dict' object has no attribute 'MSFT'

I'm using v 0.1.59

In case anyone else has this issue I realized that I had to iterate over the key-value pairs of the dictionary, so I did this:
tickers = yf.Tickers('msft aapl goog')
for key, value in tickers.tickers.items():

Then, I can access each ticker (key) in the dictionary. For example:
	pb = value.info['priceToBook']


text:
Fixed incorrect lb config reference

https://github.com/rancher/rancher/issues/1838
Awful bug that has been sitting there for a while

LGTM

repo: rancher/cattle


text:
ClassCast exception fix for selector links

https://github.com/rancher/rancher/issues/2303

LGTM


text:
Config Scale and Ready Scale in Detail Top section of workloads

On master-head - commit id: 8d9cedde9

The detail top section of workloads details - Job/CroJob/Deployments show Config Scale and Ready Scale fields.
It is applicable for Statefulsets/Deployments. Is this field required for other type of workloads?

On master-head - commit id: 33f755f18

The detail top section of workloads details - Job/CroJob/Deployments show fields as expected

repo: rancher/dashboard


text:
Secrets UI issues

All

[x] We need to add the Type of Secret to Top Header (Need design from @lvuch)

Registry:

[x] For the radio buttons, if we want Custom to be the default, then it should be at the top.

Opaque:

[x] For Data, the Add button needs to be two buttons -  This has been fixed already

Certificate

[x] In the Data tab add the header Certificate

SSH

[x] In the Data tab add the header Keys

Basic Auth

[x] In the Data tab add the header Authentication

Fixed


text:
"Drain on Upgrade" should be "No" by default for RKE2

Detailed Description
"Upgrade Strategy -> Control Plane (or Worker Nodes) -> Drain Nodes" default was switched to "Yes" per https://github.com/rancher/dashboard/issues/5618, however, this was due to taking https://github.com/rancher/rancher/issues/36969#issuecomment-1093440709 a bit too far. We only need "Delete pods using emptyDir volumes" to be checked by default if "Drain Nodes" is set to "Yes" to avoid running into issue from the comment linked.
Context
RKE1 provisioned clusters default to "Drain Nodes on Upgrade" as "No", so making this change ensures default RKE2 provisioning settings more closely match defaults for RKE1.
Note this change will also reduce the impact of https://github.com/rancher/rancher/issues/37597 as default for "Drain Nodes" will match between backend and UI (it will still be reproducible for "Delete pods using emptyDir volumes" case though).

Ticket #5829 - Test Results
With Docker on a single-node instance:
Reproduced on rancher v2.6.5-rc3:

Fresh install of rancher v2.6.5-rc3
Provision a downstream RKE2 cluster
Once provisioned, view cluster's config
Reproduced - Drain on Upgrade is set to Yes by default

Screenshot:
Step 4

Verified on rancher v2.6-4bbee5995053eb52ef447ca82de2c90b1af8b21a-head:

Fresh install of rancher v2.6-head
Provision a downstream RKE2 cluster
Once provisioned, view cluster's config
Verified - Drain on Upgrade is set to No by default;
Verified - If Drain on Upgrade is switched to Yes, Delete pods using emptyDir volumes is enabled [by default]

Screenshots:
Step 4

Step 5

authors: Josh-Diamond snasovich


text:
When editing YAML, the header of the page says "Edit Receiver in AlertmanagerConfig"

This issue is from feedback on a demo.
The header "Edit Receiver in AlertmanagerConfig" is supposed to only show on the form view, not the YAML view.
The title of the YAML page should be "Edit AlertmanagerConfig" because the receiver is a config block within the larger resource.
Note: If you go to Edit as YAML from the action menu in the receiver list view, I already fixed it. The bug is only seen when you go to Edit Config and then switch to Edit as YAML from there.

QA Template
Root cause
Query params were not included in the logic for deciding what header to show
What was fixed, or what changes have occurred
When you are editing an AlertmanagerConfig resource, and you navigate from Edit Config to Edit YAML, the as=yaml query param is added to the URL. The change now uses that param to know when the display is YAML and the header should be "Edit AlertmanagerConfig"
Areas or cases that should be tested

Install monitoring
Install Prometheus Federator
Create an AlertmanagerConfig resource
Go to the new AlertmanagerConfig and click Edit Config (the error is not seen if you go directly to YAML). Confirm the title is still "Edit Receiver in AlertmanagerConfig" when the form is shown.
Click Edit as YAML
Confirm that the title is now "Edit AlertmanagerConfig" when the YAML view is shown.

What areas could experience regressions?
Can't think of any

Pass Verified in 2.6-head Commit ID c5746d9

created alert manager config
created receiver
clicked edit config
clicked Edit as Yaml on bottom of page

Edit message at top of screen changed based on edit view as expected

authors: catherineluse ronhorton


text:
Fix: issue with displaying Errors messages

While editing an YAML file, if there's any HTTP error sent to the Footer>Banner component it will display it as [Object Object]

This PR will fixes it by looking if the label objects includes a message propriety, if so it will stringify and display the Error message.

Could you define a case to reproduce an error containing a message and reference the issue if exists?

I noticed that any response will an error (validation, network status etc..) will be affected. One way to reproduce would be:

Edit any Pod configuration vía YAML and change any boolean value to something invalid like falsea , this will return a 400 Error and you'll be able to preview it.

@richard-cox Could you give this the once-over - is this something we want to get in for 2.6.4?

authors: nwmac scures


text:
fix growl text overflow

Summary
growl components cannot scroll when the text in the message is long, or when there are a large number of messages

Fixes #

Occurred changes and/or fixed issues

Technical notes summary

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

I think this requires a UX review, we shouldn't be showing so much content in a growl. cc @kwwii

I think this requires a UX review, we shouldn't be showing so much content in a growl. cc @kwwii

There's one situation to consider: there's only one message, but it's a very long one. If we don't allow scrolling, then a portion of the message is invisible。

Think the aim of the growls are to show short, simple messages. Anything that requires scrolling kind of breaks that pattern


text:
Investigate Hugo app failures (drone failures)

We should spend some time to investigate why hugo crashes / times out in drone-pr some of the time. It's the same generic message each time. The workaround is to restart (sometimes more than once) which slows down work.
Drone should not be at fault. The issue seems to be coming from hugo.

This seems to be failing more frequently and is slowing down my effort to get k3s docs in.

I think we can close this issue because to my knowledge, we have not had a drone failure in some time. Please let me know if it happens again.

authors: catherineluse davidnuzik

repo: rancher/docs


text:
Change "Machine Count" to be number of machines selected

When I select some machines in the machine inventory and click "Create Elemental Cluster" from the dropdown, I correctly get pushed over to the cluster creation page. Unless you are paying attention, it's easy to miss that you need to increment the machine count for the machine pool. If you don't do this, you only get a single node cluster.

@agracey so the number of Machine Counts should match the number of Machine Inventories at all times? If I add 30 mach. inv. it should have 30 machine counts? Just for confirmation, thank you

Yes, that is correct.

That's a good question. I wonder if anything would break if it was set to 0

I just tried with 0 and I can create it:

Then:

@agracey @juadk the default for every other cluster type is 1. I am not knowledgeable on K8s, but does it even make sense to create a cluster with 0 Machine Counts? What if they want to create a cluster with any other purpose?

In the general case, there is a use for clusters without nodes as it can be very helpful to keep the control plane for, say, EKS alive but not have any nodes attached. I've done this several times when I didn't want to rebuild everything after a demo but I also didn't want to pay for the cluster to be running.
For our case, I think it might be a bit awkward to have a 0 be allowed but I don't think it makes sense to override the defaults.
Additionally, the place where I think we need to be careful is that an admin might be setting up clusters (and selectors) before the MachineInventories exists to be included. I don't know what the right UX is for this but my instinct is that most admin's who are doing this type of pre-provisioning would be working with the API as you wouldn't manually go through this process 5000 times.

Then, let's close it :smile:

authors: aalves08 agracey juadk

repo: rancher/elemental-ui


text:
WIP: latest k3s 0.10.0

Tested on VirtualBox as server node.
Making WIP until https://github.com/rancher/k3s/pull/946 is done.

@bhale it looks like rancher/k3s#946 has been closed in favor of rancher/k3s#962

authors: bhale dweomer


text:
Add load test results to docs content

Need to add some baseline perf documentation, based on the initial writeup at https://gist.github.com/brandond/32f8c4846b9f71d6c145c26afced7ed8
Would like to add a couple things to the existing info:

Warnings about burstable instance types / CPU credit exhaustion (runs great until you don't have burstable credits)
Additional resource figures for same nodes running Rancher 2.5 monitoring the local cluster

Docs PR: https://github.com/rancher/docs/pull/2836

Looks like this is merged in. Closing.

authors: brandond davidnuzik


text:
Regions

rancher/rancher#9839

Before review - Need to update code, similar to changes mentioned in https://github.com/rancher/rancher-dns/pull/69.

repo: rancher/lb-controller


text:
UI: Enhance the dashboard

It's better for the user to see the overview of the whole Longhorn system in the dashboard, in the format as similar to Rancher dashboard for the cluster:

Available storage space vs maximum storage space (- reserved storage space).
Healthy attached volume vs unattached volume vs faulted volume vs total volumes.
Healthy node vs Total nodes.

Done.

repo: rancher/longhorn


text:
Passing AWS credentials to backup snapshots to S3

Hi,
I was trying to backup a snapshot to s3 using the following command:
sudo docker exec -it Container_ID longhorn backups create snapshotName --dest S3_destination_URL
Above command doesn't work, if the credentials are added after the longhorn controller starts inside the container.
I had to modify the file package/Dockerfile to generate the AWS credentials file. And then built the longhorn image.
Is there any way to pass these credentials with the backup create/restore commands ?

You can use AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY environment variable instead. See https://github.com/aws/aws-sdk-go#configuring-credentials

authors: payes yasker


text:
remove '-f' in docker tag command

when we use lastest version of docker, the '-f' is deprecated. like:
ubuntu@ubuntu:~/docker-from-scratch$ docker tag -f ubuntu:14.04 ubuntu:myself
Warning: '-f' is deprecated, it will be removed soon. See usage.
ubuntu@ubuntu:~/docker-from-scratch$ docker version
Client:
 Version:      1.10.0-dev
 API version:  1.22
 Go version:   go1.5.1
 Git commit:   9165700
 Built:        Mon Dec  7 17:59:10 2015
 OS/Arch:      linux/arm64

Server:
 Version:      1.10.0-dev
 API version:  1.22
 Go version:   go1.5.1
 Git commit:   9165700
 Built:        Mon Dec  7 17:59:10 2015
 OS/Arch:      linux/arm64

so just remove it.
Signed-off-by: Wang Long long.wanglong@huawei.com

Thanks @datawolf!
I'll merge this when we move the build to docker-1.10 and -f flag becomes unnecessary. So, don't close it ;)

@imikushin , I will close this pr, and open another.

authors: datawolf imikushin

repo: rancher/os-images


text:
API in version 2

We are trying to create a project, assign members & owners, create a deployment with persistent storage all through the API.  The lack of documentation is a severe limitation on our efforts.

Consolidating into https://github.com/rancher/rancher-docs/issues/583.

repo: rancher/rancher-docs


text:
label propagation to nodes doesnt happen when using aws as the cloud provider in k8s

Rancher versions:
rancher/server: 1.6.10
rancher/agent: 1.2.6
Steps to Reproduce:

deploy a k8s environment that uses aws as the cloud provider
use the ec2 driver to launch hosts, add labels to hosts (understandably this isnt supported officially, it seems to mostly work. And the ability to use machine drivers would rock)

Results:
no labels get propagated to the k8s nodes
Following errors seen in rancher/kubernetes-agent logs:
12/7/2017 3:52:30 PMtime="2017-12-07T23:52:30Z" level=info msg="Skipping event: [ADDED] for namespace: kube-system"
12/7/2017 3:52:30 PMtime="2017-12-07T23:52:30Z" level=info msg="Received event: [ADDED] for Service: default/kubernetes, Handling event."
12/7/2017 3:52:30 PMtime="2017-12-07T23:52:30Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:30 PMtime="2017-12-07T23:52:30Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:30 PMtime="2017-12-07T23:52:30Z" level=info msg="Received event: [ADDED] for Service: kube-system/tiller-deploy, Handling event."
12/7/2017 3:52:31 PMtime="2017-12-07T23:52:31Z" level=info msg="Received event: [ADDED] for Service: kube-system/kubernetes-dashboard, Handling event."
12/7/2017 3:52:31 PMtime="2017-12-07T23:52:31Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:31 PMtime="2017-12-07T23:52:31Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:32 PMtime="2017-12-07T23:52:32Z" level=info msg="Received event: [ADDED] for Service: kube-system/monitoring-grafana, Handling event."
12/7/2017 3:52:32 PMtime="2017-12-07T23:52:32Z" level=info msg="Received event: [ADDED] for Service: kube-system/monitoring-influxdb, Handling event."
12/7/2017 3:52:32 PMtime="2017-12-07T23:52:32Z" level=info msg="Received event: [ADDED] for Service: kube-system/heapster, Handling event."
12/7/2017 3:52:32 PMtime="2017-12-07T23:52:32Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:32 PMtime="2017-12-07T23:52:32Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:33 PMtime="2017-12-07T23:52:33Z" level=info msg="Received event: [ADDED] for Service: kube-system/kube-dns, Handling event."
12/7/2017 3:52:33 PMtime="2017-12-07T23:52:33Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:33 PMtime="2017-12-07T23:52:33Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:35 PMtime="2017-12-07T23:52:35Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:35 PMtime="2017-12-07T23:52:35Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:36 PMtime="2017-12-07T23:52:36Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:36 PMtime="2017-12-07T23:52:36Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:38 PMtime="2017-12-07T23:52:38Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"
12/7/2017 3:52:38 PMtime="2017-12-07T23:52:38Z" level=error msg="Error getting node: [sank8saws] by name from kubernetes, err: [nodes \"sank8saws\" not found]"```

Tested with the following parameters:

rancher server v1.6.15-rc5
created a k8s environment with aws cloud provider
created 15 hosts, in 3, 4, 8 batches, each with a different set of labels.
in all cases the label propagated correctly.

I was not able to reproduce this issue with latest RC.

The problem is with node names.
K8s defaults to use aws internal instance hostnames, while rancher uses "host names" defined in while creating hosts.
I tried to update --override-hostname with kubelet to use the rancher host names with k8s, but using --cloud-provider=aws overrides --override-hostname.
I will try to fix this in kubernetes-agent.

Fix is with kubernetes-agent:v0.6.7

Tested with master 1.6-development.
Created a K8s environment with AWS hosts and added labels while adding hosts.
kubectl describe node nodename showed the label correctly
Label was added after the nodes were created and labels were displayed correctly
LAPTOP-6CQEFUBT:~ soumya$ kubectl describe node soumyalabelpropagation1
Name:			soumyalabelpropagation1
Role:
Labels:			awstest=value
			beta.kubernetes.io/arch=amd64
			beta.kubernetes.io/instance-type=rancher
			beta.kubernetes.io/os=linux
			failure-domain.beta.kubernetes.io/region=Region1
			failure-domain.beta.kubernetes.io/zone=FailureDomain1
			io.rancher.host.os=linux
			io.rancher.host.provider=aws
			io.rancher.host.region=us-west-1
			io.rancher.host.zone=us-west-1b
			kubernetes.io/hostname=soumyalabelpropagation1
			labelagain=test

authors: aemneina deniseschannon moelsayed soumyalj

repo: rancher/rancher


text:
Can't add a stage when I edit a Pipeline

Rancher versions: 2.0 master 2/27
Steps to Reproduce:

Create a pipeline
Edit Pipeline

Results:  No Add a Stage button

Version - 2.0 master 2/28
Verified fixed


text:
[Feature Request] Reusable Cloud Config

Just like node templates I would like a way to save and reuse cloud config. Right now I am having to fill out the config each time I create a new cluster but it is usually the same config.

Close in favor of https://github.com/rancher/rancher/issues/14337

authors: loganhz mitchellmaler


text:
Reducing the resource quota at project level below the namespace resources consumed should not be allowed

Rancher versions:
rancher/server or rancher/rancher:master from sep 13
Steps:

Create a project with resource quota {pods=20} and default namespace quota as 5
Create two namespaces with default resource quota
Edit the project resource quota to 5 (below the consumed resource quota) which is allowed
The API shows the below:

"resourceQuota": {
"limit": {
"pods": "5",
"type": "/v3/schemas/resourceQuotaLimit"
},
"type": "/v3/schemas/projectResourceQuota",
"usedLimit": {
"pods": "10",
"type": "/v3/schemas/resourceQuotaLimit"
}
},

For a project with resource quota assigned, reducing the quota should be allowed only by taking into account the used limit. Reducing the quota below the used limit should not be allowed.

Tested with v2.1.0-rc1. Reducing the resourcequota at the project level below the namespace resource quota errors out as expected.
As an example, the usedLimit is 15 and the project resourcequota is 20.
namespaceDefaultResourceQuota": {
"limit": {
"pods": "5",
"type": "/v3/schemas/resourceQuotaLimit"
},
"type": "/v3/schemas/namespaceResourceQuota"
},
"namespaceId": null,
"podSecurityPolicyTemplateId": "",
"resourceQuota": {
"limit": {
"pods": "20",
"type": "/v3/schemas/resourceQuotaLimit"
},
"type": "/v3/schemas/projectResourceQuota",
"usedLimit": {
"pods": "15",
"type": "/v3/schemas/resourceQuotaLimit"
}
},

Edited the project resourcequota to 12 and the below error message was displayed.

The message should be "Validation failed in API: resourceQuota BELOW the used limit on fields: pods=15
Also, editing the projectquota right after the above error displays the reduced value in UI. UI does not get updated until a refresh is done. UI issue will be filed.

Tested with rancher v2.1.0-rc2 . The error message is fixed for the use case described above.
Error message below


text:
Linked containers running on different hosts cannot ping

TLDR;
cross-host network is not working

I've got a simple 2-3 component service, consisting of redis instance, webdis instance and an optional load balancer.
Here is my docker-compose.yml:
haproxy:
  image: 'tutum/haproxy:0.1'
  environment:
    - BACKEND_PORT=7379
  links:
    - 'webdis'
  ports:
    - '8000:80'
    - '1936:1936'
webdis:
  image: 'anapsix/webdis'
  ports:
   - '7379:7379'
  links:
   - 'redis'
redis:
  image: 'anapsix/redis:latest'

I start service up with rancher-compose up, which is reflected in Rancher Web-UI.

However, it appears that webdis instance cannot talk to redis instance (and haproxy cannot connect to webdis as well) even though the containers are linked.
Hostname redis is properly resolvable from withing webdis, but pings fail.
### webdis container
/ # ip a s eth0
23: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 02:96:4a:73:08:55 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.7/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.42.14.165/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::96:4aff:fe73:855/64 scope link
       valid_lft forever preferred_lft forever

/ # ping -c 4 redis
PING redis (10.42.247.116): 56 data bytes
--- redis ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

Yet haproxy container, that runs on the same host can ping redis, though I have to use the IP, since redis is not linked to haproxy.
### haproxy container
/ # ip a s eth0
23: eth0: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default
    link/ether 02:96:4a:19:f2:2f brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.7/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet 10.42.168.239/16 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 fe80::96:4aff:fe19:f22f/64 scope link
       valid_lft forever preferred_lft forever

/ # ping -c 4 10.42.247.116
PING 10.42.247.116 (10.42.247.116) 56(84) bytes of data.
64 bytes from 10.42.247.116: icmp_seq=1 ttl=64 time=0.106 ms
64 bytes from 10.42.247.116: icmp_seq=2 ttl=64 time=0.074 ms
64 bytes from 10.42.247.116: icmp_seq=3 ttl=64 time=0.079 ms
64 bytes from 10.42.247.116: icmp_seq=4 ttl=64 time=0.054 ms
--- 10.42.247.116 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms

environment
Rancher and RancherOS on bare metal
RancherOS v0.3.3
rancher/agent-instance:v0.3.1
rancher/agent:v0.7.9
CATTLE_RANCHER_SERVER_IMAGE=v0.25.0
CATTLE_CATTLE_VERSION=v0.58.0

I have the same issue across cloud providers on VMs (GCE & AWS) while IPSEC UDP ports 500 and  4500 are allowed to  0.0.0.0/0, but haven't had time to investigate further yet. Funny enough, it seems to work inside 3 hosts in GCE but doesn't reach AWS.

@Kelindar I'm running it on two physical hosts in a rack next to each other.. No extra firewall rules.. So, not really sure what's up

Just got the same issue again with 3 hosts on GCE, running rancher v0.30.0-rc2
Messaging:
  ports:
  - 4000:4000/tcp
  - 4001:4001/tcp
  - 8082:8082/tcp
  restart: always
  environment:
    GNATS_LOG: 'true'
  domainname: ''
  labels:
    io.rancher.scheduler.global: 'true'
  tty: true
  hostname: messaging
  image: emitter/bus
  privileged: true
  stdin_open: true

@ibuildthecloud any idea why this might be happening?

@anapsix Was the webdis container the only container on the host?
@Kelindar Do you only have 1 container on each host?
There is a known issue https://github.com/rancher/rancher/issues/486 where sometimes (not always) when you only have 1 container on the host, the containers are unable to ping other containers. The workaround is to either add another container to the hosts or to restart the container in the service.
I was able to reproduce @anapsix set up and adding another container on the host resolved the inability to ping.

@deniseschannon webdis was the only non-rancher container on the host, i.e. in addition to webdis, there was also rancher/agent and rancher/agent-instance images running..

@anapsix Not sure if you still have this setup, but next time can you try to add another container or restarting webdis to the host that is unable to ping?

@deniseschannon restarting doesn't help.. (I assumed you wanted me to docker restart container_id)

could you try adding another container on the host? typically, restarting should have fixed it, if it was similar to the 486 issue, but maybe a new container must be added. Are all your hosts RancherOS? That's how I had set up my setup when I went to reproduce and made a fix by adding another container.

@deniseschannon all the hosts are running RancherOS.. I've checked the rancher/agent logs and I this is what I see during the restart:
time="2015-07-28T21:24:51Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"die\", ID:\"2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a\", From:\"anapsix/webdis:latest\", Time:1438118691}"
time="2015-07-28T21:24:51Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"stop\", ID:\"2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a\", From:\"anapsix/webdis:latest\", Time:1438118691}"
time="2015-07-28T21:25:16Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a\", From:\"anapsix/webdis:latest\", Time:1438118716}"
time="2015-07-28T21:25:16Z" level="info" msg="Assigning IP [10.42.14.165/16], ContainerId [2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a], Pid [31115]"
time="2015-07-28T21:25:16Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a\", From:\"-simulated-\", Time:0}"
time="2015-07-28T21:25:16Z" level="info" msg="Container locked. Can't run StartHandler. ID: [2f4262e2a85dbf09a2987e4658b6e79bbea3240d831de172d1b24245b989e69a]"

I've started anapsix/pgsql container on the same home, and was able to ping pgsql -> webdis and webdis -> pgsql, but still cannot ping any container on another host from wither pgsql or webdis.
Logs from rancher/agent while anapsix/pgsql was starting up:
time="2015-07-28T21:32:21Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"die\", ID:\"38024a188ae71d49b53f1991335ab4b67aae7bf4db6c4813f2a9da5780007189\", From:\"anapsix/pgsql:latest\", Time:1438119141}"
time="2015-07-28T21:32:22Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"stop\", ID:\"38024a188ae71d49b53f1991335ab4b67aae7bf4db6c4813f2a9da5780007189\", From:\"anapsix/pgsql:latest\", Time:1438119142}"
time="2015-07-28T21:32:30Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"destroy\", ID:\"38024a188ae71d49b53f1991335ab4b67aae7bf4db6c4813f2a9da5780007189\", From:\"anapsix/pgsql:latest\", Time:1438119150}"
time="2015-07-28T21:33:41Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"b38f0d2a514562e28f412530a05e63bf99647885d50cae60d9011af55502bb23\", From:\"anapsix/pgsql:latest\", Time:1438119221}"
time="2015-07-28T21:33:41Z" level="info" msg="Assigning IP [10.42.201.79/16], ContainerId [b38f0d2a514562e28f412530a05e63bf99647885d50cae60d9011af55502bb23], Pid [3199]"
time="2015-07-28T21:33:41Z" level="info" msg="Processing event: &docker.APIEvents{Status:\"start\", ID:\"b38f0d2a514562e28f412530a05e63bf99647885d50cae60d9011af55502bb23\", From:\"-simulated-\", Time:0}"
time="2015-07-28T21:33:41Z" level="info" msg="Container locked. Can't run StartHandler. ID: [b38f0d2a514562e28f412530a05e63bf99647885d50cae60d9011af55502bb23]"

I've upgraded server to latest v0.31.0 and now having trouble starting all the services in the stack via rancher-compose (see #1720). When I start the failed service via WebUI, linked container does not resolve and is unpingable even by IP.

rancher-compose #1720 issue solved - I've been using older version..
after upgrade, all services in the stack started.. though I still cannot ping redis container from webdis (they are running on different hosts)

I had a similar issue due to firewall.
I know that you already said they are both next to each other but it is worth checking that 500/UDP, 4500/UDP are accessible both ways against the IPs listed in the rancher GUI.
As RancherOS is a minimal image, could you maybe spawn up centos/ubuntu and test via netcat?
E.g.
Test 500/UDP, between both servers
nc -luv 500
nc -vu server.ip.address.here 500

type hi or something, you should be able to see it on the other server

and
Test 4500/UDP, between both servers
nc -luv 4500
nc -vu server.ip.address.here 4500

type hi or something, you should be able to see it on the other server

seems like hosts can reach each other over 500/UDP and 4500/UDP @mryuha

nick -> matt
[rancher@nick ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu matt 500
hello
Connection to matt 500 port [udp/isakmp] succeeded!

[rancher@nick ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu matt 4500
hello
Connection to matt 4500 port [udp/ipsec-nat-t] succeeded!

matt -> nick
[rancher@matt ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu nick 500
hello
Connection to nick 500 port [udp/isakmp] succeeded!

[rancher@matt ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu nick 4500
hello
Connection to nick 4500 port [udp/ipsec-nat-t] succeeded!

Can you try with multicloud/netcat image instead of ubuntu.
I receive "Connection to host 500 port [udp/isakmp] succeeded!" too in ubuntu's nc even though the port is blocked.

@mryuha, I think it's not lying..
[rancher@nick ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu matt 4253
[rancher@nick ~]$ docker run -it --rm --net=host ubuntu timeout 5 nc -vu matt 4500
Connection to matt 4500 port [udp/ipsec-nat-t] succeeded!

grrr.. :disappointed: I can't even stop the agent containers without rebooting to test those ports..
getting bunch of these from the kernel
[367976.269480] INFO: task docker:683 blocked for more than 120 seconds.
[367976.346986]       Not tainted 3.19.8-ckt1-rancher #1
[367976.407782] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[367976.503220] docker          D ffff88100c3fb780     0   683    580 0x00000000
[367976.589230]  ffff88100c3fb780 ffffffff8102f9cd 0000000000012640 ffff88100c3fb780
[367976.679955]  ffff881009e4bfd8 ffff88040fcd2640 ffffffff81a6e890 ffffffff81a6e894
[367976.770644]  ffff88100c3fb780 ffffffff81a6e898 00000000ffffffff 0000000000000000
[367976.861288] Call Trace:
[367976.891913]  [<ffffffff8102f9cd>] ? default_send_IPI_mask_sequence_phys+0x38/0x6d
[367976.983187]  [<ffffffff813fbb9b>] ? schedule_preempt_disabled+0x6/0x8
[367977.061708]  [<ffffffff813fc73a>] ? __mutex_lock_slowpath+0x97/0xf7
[367977.138222]  [<ffffffff813fc7b0>] ? mutex_lock+0x16/0x25
[367977.203281]  [<ffffffff81334a70>] ? copy_net_ns+0x7a/0xec
[367977.269330]  [<ffffffff8105bb59>] ? create_new_namespaces+0xf0/0x164
[367977.346811]  [<ffffffff8105bc2c>] ? copy_namespaces+0x5f/0x81
[367977.417079]  [<ffffffff8104591f>] ? copy_process.part.36+0xf15/0x15b1
[367977.495687]  [<ffffffff81046133>] ? do_fork+0xb1/0x207
[367977.558644]  [<ffffffff81121ec9>] ? __fd_install+0x1c/0x4e
[367977.625772]  [<ffffffff813fe429>] ? stub_clone+0x69/0x90
[367977.690758]  [<ffffffff813fe109>] ? system_call_fastpath+0x12/0x17
Message from syslogd@rancher at Aug  7 20:56:15 ...
 kernel:[367888.865904] unregister_netdevice: waiting for lo to become free. Usage count = 2

I just going to wipe it and try with Jessie..

Well.. installed Jessie, Docker and Rancher on top and same issue..
When two container are running on the same host - all is good, when they are on different hosts, no pings going through.

I've shut down the Agents and trying to confirm 500/UDP and 4500/UDP connectivity to no avail.
I've flushed iptables rules with 'iptables -F'..
nick:
netcat -l -u -p 4500

matt:
echo this is a test  | nc -u nick 4500

and nothing.. sending some text from nick to nick works :(
so.. cleary, rancher network wouldn't work when I cannot even run nc ping between the hosts.. except for, I have no idea why it won't work..

hmm.. on nick:
20:20:00.591384 IP (tos 0x0, ttl 64, id 35234, offset 0, flags [DF], proto UDP (17), length 34)
    10.20.0.22.43415 > 10.20.0.21.4500: [udp sum ok] UDP-encap: [|ESP]

on matt:
20:20:02.187178 IP (tos 0x0, ttl 64, id 35234, offset 0, flags [DF], proto UDP (17), length 34)
    10.20.0.22.43415 > 10.20.0.21.4500: [bad udp cksum 0x1472 -> 0xec77!] UDP-encap: [|ESP]

@anapsix does nc on other ports (e.g. 80 or 12345) work?  What kind of network are they on? Are nick and matt VMs (on the same host?), bare metal, etc?
Consumer home routers sometimes have IPSec config options for pass through and such, maybe that's poorly implemented and mangles IPSec that is purely within the network?

What makes it weird @vincent99, is that both hosts are physical SuperMicro based servers and are able to communicate on alternative UDP or TCP ports. In fact at some point I was able to have a successful nc test over 4500/UDP. All other servers in the rack pass 4500/UDP test just fine.
Both servers are connected to datacenter grade Cumulus switch with network interfaces connected to the ports on the same vlan/bridge.

When you say shutting down the agents, are you stopping the "network agent" container (rancher/agent-instance image) that shows port/ 500/4500? The other rancher/agent container is not the one that the IPSec server runs in.

Yep, I docker kill them all

Alright, I see why I'm having trouble testing..
Packets are being dropped, which is confirmed by dropped counter increasing when I do an "echo | nc .... I also noticed a CATTLE_PREROUTING` DNAT rule in iptables:
Chain CATTLE_PREROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
    6   636 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:4500 to:10.42.25.184:4500
   26  8444 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:500 to:10.42.25.184:500

When I've flushed iptables, I did it with iptables -F, which does not clear NAT rules.. iptables -F -t nat does the trick.
Once all iptables rules are flushed, connectivity test is successful:
anapsix@nick:~$ echo hello | nc -uv matt 500
matt [10.20.0.22] 500 (isakmp) open

anapsix@matt:~$ sudo nc -luv -p 500
listening on [any] 500 ...
connect to [10.20.0.22] from nick [10.20.0.21] 53692
hello

So... no issues with my connectivity..

when nick runs webdis (10.42.175.248) and matt runs redis (10.42.205.249), I can ping redis container from matt, but cannot ping webis container from nick.
At first glance, iptables rules seem find, but there's gotta be something off..
I feel like that should not matter, but I did not mention it before: nick runs Rancher Server and Agent(s), while _matt runs only Agent(s).
iptables on nick:
$ iptables -vL -n
Chain INPUT (policy ACCEPT 431K packets, 233M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 2 packets, 120 bytes)
 pkts bytes target     prot opt in     out     source               destination
 124K   78M DOCKER     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0
 8096 5083K ACCEPT     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
 130K   32M ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0
  615 40566 ACCEPT     all  --  docker0 docker0  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT 450K packets, 295M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination
 108K   72M ACCEPT     tcp  --  !docker0 docker0  0.0.0.0/0            172.17.0.1           tcp dpt:8080
 6939  861K ACCEPT     udp  --  !docker0 docker0  0.0.0.0/0            172.17.0.4           udp dpt:4500
    1   424 ACCEPT     udp  --  !docker0 docker0  0.0.0.0/0            172.17.0.4           udp dpt:500

$ iptables -vL -n -t nat
Chain PREROUTING (policy ACCEPT 11494 packets, 699K bytes)
 pkts bytes target     prot opt in     out     source               destination
16185  980K CATTLE_PREROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0
10754  647K DOCKER     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 10493 packets, 632K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 10941 packets, 770K bytes)
 pkts bytes target     prot opt in     out     source               destination
   47  2940 DOCKER     all  --  *      *       0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 11140 packets, 782K bytes)
 pkts bytes target     prot opt in     out     source               destination
12147  849K CATTLE_POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0
   67  4397 MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0
    0     0 MASQUERADE  tcp  --  *      *       172.17.0.1           172.17.0.1           tcp dpt:8080
    0     0 MASQUERADE  udp  --  *      *       172.17.0.4           172.17.0.4           udp dpt:4500
    0     0 MASQUERADE  udp  --  *      *       172.17.0.4           172.17.0.4           udp dpt:500

Chain CATTLE_POSTROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
    2   102 ACCEPT     all  --  *      *       10.42.0.0/16         169.254.169.250
    0     0 MASQUERADE  tcp  --  *      *       10.42.0.0/16        !10.42.0.0/16         masq ports: 1024-65535
    0     0 MASQUERADE  udp  --  *      *       10.42.0.0/16        !10.42.0.0/16         masq ports: 1024-65535
    0     0 MASQUERADE  all  --  *      *       10.42.0.0/16        !10.42.0.0/16
    4   298 MASQUERADE  tcp  --  *      !docker0  172.17.0.0/16        0.0.0.0/0            masq ports: 1024-65535
  943 63541 MASQUERADE  udp  --  *      !docker0  172.17.0.0/16        0.0.0.0/0            masq ports: 1024-65535

Chain CATTLE_PREROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
 4639  278K DNAT       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL tcp dpt:8080 to:172.17.0.1:8080
    2   120 DNAT       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL tcp dpt:7379 to:10.42.175.248:7379
    0     0 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:4500 to:10.42.107.194:4500
    0     0 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:500 to:10.42.107.194:500

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
  199 11916 DNAT       tcp  --  !docker0 *       0.0.0.0/0            0.0.0.0/0            tcp dpt:8080 to:172.17.0.1:8080
    0     0 DNAT       udp  --  !docker0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:4500 to:172.17.0.4:4500
    0     0 DNAT       udp  --  !docker0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:500 to:172.17.0.4:500

iptables on matt:
$ iptables -vL -n
Chain INPUT (policy ACCEPT 402K packets, 157M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain FORWARD (policy ACCEPT 3 packets, 668 bytes)
 pkts bytes target     prot opt in     out     source               destination
15351 5869K DOCKER     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0
14801 5831K ACCEPT     all  --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
10857 1098K ACCEPT     all  --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0
  547 37536 ACCEPT     all  --  docker0 docker0  0.0.0.0/0            0.0.0.0/0

Chain OUTPUT (policy ACCEPT 448K packets, 222M bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain DOCKER (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     udp  --  !docker0 docker0  0.0.0.0/0            172.17.0.3           udp dpt:4500
    0     0 ACCEPT     udp  --  !docker0 docker0  0.0.0.0/0            172.17.0.3           udp dpt:500

$ iptables -vL -n -t nat
Chain PREROUTING (policy ACCEPT 18487 packets, 1110K bytes)
 pkts bytes target     prot opt in     out     source               destination
18489 1110K CATTLE_PREROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0
18255 1095K DOCKER     all  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT 18221 packets, 1093K bytes)
 pkts bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 18497 packets, 1308K bytes)
 pkts bytes target     prot opt in     out     source               destination
    2   168 DOCKER     all  --  *      *       0.0.0.0/0           !127.0.0.0/8          ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT 18669 packets, 1319K bytes)
 pkts bytes target     prot opt in     out     source               destination
18773 1326K CATTLE_POSTROUTING  all  --  *      *       0.0.0.0/0            0.0.0.0/0
  104  6572 MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0
    0     0 MASQUERADE  udp  --  *      *       172.17.0.3           172.17.0.3           udp dpt:4500
    0     0 MASQUERADE  udp  --  *      *       172.17.0.3           172.17.0.3           udp dpt:500

Chain CATTLE_POSTROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 ACCEPT     all  --  *      *       10.42.0.0/16         169.254.169.250
    0     0 MASQUERADE  tcp  --  *      *       10.42.0.0/16        !10.42.0.0/16         masq ports: 1024-65535
    0     0 MASQUERADE  udp  --  *      *       10.42.0.0/16        !10.42.0.0/16         masq ports: 1024-65535
    0     0 MASQUERADE  all  --  *      *       10.42.0.0/16        !10.42.0.0/16
   48  2880 MASQUERADE  tcp  --  *      !docker0  172.17.0.0/16        0.0.0.0/0            masq ports: 1024-65535
   48  3216 MASQUERADE  udp  --  *      !docker0  172.17.0.0/16        0.0.0.0/0            masq ports: 1024-65535

Chain CATTLE_PREROUTING (1 references)
 pkts bytes target     prot opt in     out     source               destination
    1   132 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:4500 to:10.42.239.178:4500
    1   412 DNAT       udp  --  *      *       0.0.0.0/0            0.0.0.0/0            ADDRTYPE match dst-type LOCAL udp dpt:500 to:10.42.239.178:500

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination
    0     0 DNAT       udp  --  !docker0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:4500 to:172.17.0.3:4500
    0     0 DNAT       udp  --  !docker0 *       0.0.0.0/0            0.0.0.0/0            udp dpt:500 to:172.17.0.3:500

quick question: is the IP on the host that is also running rancher server showing the rancher server IP? if not, you'll need to re-add the host with a modified command.
http://docs.rancher.com/rancher/rancher-ui/infrastructure/hosts/custom/#samehost
afterwards, restart the network agent.

Not sure what you mean @deniseschannon..
The IPs of Hosts in Infrastructure/Hosts are private and are accurately displayed.
The instance of the rancher/server container as displayed in Instrastructure/Constainers is 172.17.0.1 and that certainly is incorrect.
I've tried starting the Agent (on host running server) with -e CATTLE_AGENT_IP=<IP> with private IP and public IP.. But now I just cannot manage to start my 2 service stack with each service running on different hosts. Before, if it both containers started on the same host, all I needed to do is to shut it down and try again..

@anapsix Could you email me at denise @ rancher.com?

SOLUTION
On machines with multiple interfaces (and IPs) and server running on the same host as one of the agents, make sure to start Rancher Agent with -e CATTLE_AGENT_IP=$IPADDRESS.
Where $IPADDRESS is IP of the host where this Rancher Agent is being started and it's in the same network (private vs public vs other private) on all servers running Rancher Agent. Otherwise, even though iptables rules are fund, IPSec rules inside Network Agent (rancher/agent-instance) get funky and will not function properly.
After restarting rancher/agent with proper CATTLE_AGENT_IP, make sure to restart any existing Network Agents.
Check "Infrastructure > Hosts" in WebUI to make sure all Agents have IPs on the same network.
Thanks Rancher folks!

not working for me :(

@virtuman Based on your comments on this issue and the load balancer stuck in initializing issue, it sounds as if you have cross host communication issues.
please take a look to see if any of the troubleshooting FAQs might help you solve those issues.
http://docs.rancher.com/rancher/latest/en/faqs/troubleshooting/

@anapsix you made my day :+1:
For other folks having issues with network agents not being able to communicate between hosts on AWS and Rancher Load Balancer stuck in Initializing, you HAVE TO start the rancher agent with CATTLE_AGENT_IP=THE_PRIVATE_IP_OF_THE_EC2_INSTANCE

authors: Kelindar anapsix deniseschannon mryuha vincent99 virtuman vlad-pustiu